Search for: All records

ABSTRACT Follow-up observations of neutrino events have been a promising method for identifying sources of very-high-energy cosmic rays. Neutrinos are unambiguous tracers of hadronic interactions and cosmic rays. On 2020 June 15, IceCube detected a neutrino event with an 82.8 per cent probability of being astrophysical in origin. To identify the astrophysical source of the neutrino, we used X-ray tiling observations to identify potential counterpart sources. We performed additional multiwavelength follow-up with NuSTAR and the VLA in order to construct a broadband spectral energy distribution (SED) of the most likely counterpart. From the SED, we calculate an estimate for the neutrinos we expect to detect from the source. While the source does not have a high predicted neutrino flux, it is still a plausible neutrino emitter. It is important to note that the other bright X-ray candidate sources consistent with the neutrino event are also radio-quiet active galactic nuclei. A statistical analysis shows that 1RXS J093117.6+033146 is the most likely counterpart (87.5 per cent) if the neutrino is cosmic in origin and if it is among X-ray detectable sources. This result adds to previous results suggesting a connection between radio-quiet AGN and IceCube neutrino events. 

Abstract High-energy neutrinos are a promising tool for identifying astrophysical sources of high and ultra-high energy cosmic rays (UHECR). Prospects of detecting neutrinos at high energies (≳TeV) from blazars have been boosted after the recent association of IceCube-170922A and TXS 0506+056. We investigate the high-energy neutrino, IceCube-190331A, a high-energy starting event (HESE) with a high likelihood of being astrophysical in origin. We initiated a Swift/XRT and UVOT tiling mosaic of the neutrino localisation, and followed up with ATCA radio observations, compiling a multiwavelength SED for the most likely source of origin. NuSTAR observations of the neutrino location and a nearby X-ray source were also performed. We find two promising counterpart in the 90% confidence localisation region and identify the brightest as the most likely counterpart. However, no Fermi/LAT γ-ray source and no prompt Swift/BAT source is consistent with the neutrino event. At this point it is unclear whether any of the counterparts produced IceCube-190331A. We note that the Helix Nebula is also consistent with the position of the neutrino event, and we calculate that associated particle acceleration processes cannot produce the required energies to generate a high-energy HESE neutrino. 

Abstract Current neutrino detectors will observe hundreds to thousands of neutrinos from Galactic supernovae, and future detectors will increase this yield by an order of magnitude or more. With such a data set comes the potential for a huge increase in our understanding of the explosions of massive stars, nuclear physics under extreme conditions, and the properties of the neutrino. However, there is currently a large gap between supernova simulations and the corresponding signals in neutrino detectors, which will make any comparison between theory and observation very difficult. SNEWPY is an open-source software package that bridges this gap. The SNEWPY code can interface with supernova simulation data to generate from the model either a time series of neutrino spectral fluences at Earth, or the total time-integrated spectral fluence. Data from several hundred simulations of core-collapse, thermonuclear, and pair-instability supernovae is included in the package. This output may then be used by an event generator such as sntools or an event rate calculator such as the SuperNova Observatories with General Long Baseline Experiment Simulator (SNOwGLoBES). Additional routines in the SNEWPY package automate the processing of the generated data through the SNOwGLoBES software and collate its output into the observable channels of each detector. In this paper we describe the contents of the package, the physics behind SNEWPY, the organization of the code, and provide examples of how to make use of its capabilities. 

Abstract Developing sustainable software for the scientific community requires expertise in software engineering and domain science. This can be challenging due to the unique needs of scientific software, the insufficient resources for software engineering practices in the scientific community, and the complexity of developing for evolving scientific contexts. While open‐source software can partially address these concerns, it can introduce complicating dependencies and delay development. These issues can be reduced if scientists and software developers collaborate. We present a case study wherein scientists from the SuperNova Early Warning System collaborated with software developers from the Scalable Cyberinfrastructure for Multi‐Messenger Astrophysics project. The collaboration addressed the difficulties of open‐source software development, but presented additional risks to each team. For the scientists, there was a concern of relying on external systems and lacking control in the development process. For the developers, there was a risk in supporting a user‐group while maintaining core development. These issues were mitigated by creating a second Agile Scrum framework in parallel with the developers' ongoing Agile Scrum process. This Agile collaboration promoted communication, ensured that the scientists had an active role in development, and allowed the developers to evaluate and implement the scientists' software requirements. The collaboration provided benefits for each group: the scientists actuated their development by using an existing platform, and the developers utilized the scientists' use‐case to improve their systems. This case study suggests that scientists and software developers can avoid scientific computing issues by collaborating and that Agile Scrum methods can address emergent concerns.